Skip to content

Update ui deps sync (major) - #685

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/major-ui-deps-sync
Open

Update ui deps sync (major)#685
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/major-ui-deps-sync

Conversation

@renovate

@renovate renovate Bot commented Oct 6, 2025

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@rollup/plugin-alias (source) ^5.1.1^6.0.0 age adoption passing confidence
@rollup/plugin-commonjs (source) ^28.0.8^29.0.3 age adoption passing confidence
ava (source) ^6.4.1^8.0.1 age adoption passing confidence
svelte-check ^3.8.6^4.7.6 age adoption passing confidence
svelte-preprocess ^5.1.4^6.0.5 age adoption passing confidence
tailwindcss (source) ^3.4.18^4.3.3 age adoption passing confidence
typescript (source) ^5.9.3^7.0.2 age adoption passing confidence

Release Notes

rollup/plugins (@​rollup/plugin-alias)

v6.0.0

2025-10-28

Breaking Changes
  • feat!: ESM only. Update Node and Rollup minimum versions (#​1926)
rollup/plugins (@​rollup/plugin-commonjs)

v29.0.3

2026-05-29

Bugfixes

v29.0.2

2026-03-06

Bugfixes
  • commonjs: conditional exports (#​1952)

v29.0.1

2026-03-05

Bugfixes
  • commonjs: correctly replaces shorthand "global" property in object (#​1957)

v29.0.0

2025-10-30

Breaking Changes

v28.0.9

2025-10-24

Bugfixes
  • fix: handle node: builtins with strictRequires: auto (#​1930)
avajs/ava (ava)

v8.0.1

Compare Source

What's Changed

This release officially adds Node.js 26 support, with thanks to @​novemberborn in #​3450.

Per our policy, support for Node.js 25 has been removed.

Full Changelog: avajs/ava@v8.0.0...v8.0.1

v8.0.0

Compare Source

Breaking Changes

AVA now expects Node.js 22.20, 24.12 or newer.

Internally AVA is now fully ESM. This is possible now that Node.js supports loading ES modules using require() calls and simplifies AVA's types and internals.

If you use AVA from a CommonJS project you'll have to update your imports:

-const test = require('ava');
+const {default: test} = require('ava');

We expect an increasing number of projects to be ESM only. As per the above, CommonJS is still supported, but we don't expect cjs extensions to be used. The default file extensions are now js and mjs. Specify extensions: ['cjs', 'js', 'mjs'] for AVA to run test files with the cjs extension.

All test files (and those loaded through AVA's require config) are now loaded via import(). Use customization hooks for transpilation. The object form of the extensions configuration is no longer supported.

If you use AVA with @​ava/typescript you must upgrade that package to v7.

New Features

There's two new test modifiers courtesy of @​sindresorhus: test.skipIf() to skip a test based on a runtime condition. test.runIf() is the inverse: the test only runs when the condition is true.

test.skipIf(process.platform === 'win32')('not on Windows', t => {
	t.pass();
});

test.runIf(process.platform === 'linux')('Linux only', t => {
	t.pass();
});

These work with other modifiers like .serial and .failing:

test.serial.skipIf(process.platform === 'win32')('serial, not on Windows', t => {
	t.pass();
});

test.failing.skipIf(process.platform === 'win32')('expected failure, not on Windows', t => {
	t.fail();
});

Other Changes

  • Watch mode now ignores changes to *.tsbuildinfo files
  • TAP reporter is more defensive when restoring the original error name, thanks to @​ninper00 in #​3415
  • Reported errors when throwsAsync/notThrowsAsync are not awaited have been improved by @​sindresorhus in #​3436

New Contributors

Full Changelog: avajs/ava@v7.0.0...v8.0.0

v7.0.0

Compare Source

What's Changed

  • Replace strip-ansi with node:util.stripVTControlCharacters by @​fisker in #​3403
  • Remove support for Node.js 18 and 23; require 20.19 or newer, 22.20 or newer or 24,12 or newer; update dependencies including transitive glob by @​novemberborn in #​3416

Full Changelog: avajs/ava@v6.4.1...v7.0.0

sveltejs/language-tools (svelte-check)

v4.7.6

Compare Source

Patch Changes
  • fix: don't log an error for vite configs without a Svelte plugin (#​3091)

  • fix: handle SvelteKit 3 having its config merged at the top level (#​3104)

v4.7.5

Compare Source

Patch Changes

v4.7.4

Compare Source

Patch Changes
  • fix: support TypeScript 7 Stable under npm alias (#​3073)

v4.7.3

Compare Source

Patch Changes
  • feat: zero-config +error.svelte props (#​3076)

v4.7.2

Compare Source

Patch Changes
  • fix: resolve tsgo bin path with package.json (#​3074)

  • fix: report tsconfig errors in --tsgo-experimental-api (#​3070)

v4.7.1

Compare Source

Patch Changes
  • fix: correctly parse --tsgo-experimental-api flag (#​3067)

v4.7.0

Compare Source

Minor Changes
  • feat: add --config option (#​3066)

  • feat: svelte-check tsgo support with experimental api (#​3036)

Patch Changes

v4.6.0

Compare Source

Minor Changes
  • feat: support reading Svelte config from vite.config.js/ts (#​3031)
Patch Changes

v4.5.0

Compare Source

Minor Changes
  • feat: support Svelte 5 declaration tags (#​3033)
Patch Changes
  • fix: properly handle props with the name slot inside Svelte 5 snippets (#​3030)

  • feat: add support for svelte config ts/mts files (#​3009)

v4.4.8

Compare Source

Patch Changes
  • feat: typescript 6.0 support (#​2985)

v4.4.7

Compare Source

Patch Changes
  • fix: flush stdout/stderr before exit (#​3014)

  • fix: report diagnostics in tsconfig.json (#​3005)

v4.4.6

Compare Source

Patch Changes
  • fix: prevent config loading message in svelte-check --incremental (#​2974)

  • fix: resolve svelte files with NodeNext in --incremental/tsgo (#​2990)

  • perf: various optimization with ast walk (#​2969)

  • fix: prevent error with escape sequence in attribute (#​2968)

  • fix: typescript 6.0 compatibility (#​2988)

v4.4.5

Compare Source

Patch Changes
  • fix: use Promise for async kit handler return types (#​2966)

v4.4.4

Compare Source

Patch Changes
  • fix: more robust detection of lang="ts" attribute (#​2957)

  • fix: pass filename to warningFilter (#​2959)

  • fix: resolve svelte files under path alias in --incremental/tsgo mode (#​2955)

v4.4.3

Compare Source

Patch Changes
  • fix: respect @ts-ignore etc comments within tags (#​2950)

v4.4.2

Compare Source

Patch Changes
  • fix: resolve shims correctly in --incremental/tsgo mode (cd1ff2f)

  • fix: include references in generated tsconfig.json in --incremental/tsgo mode (1990f74)

v4.4.1

Compare Source

Patch Changes
  • fix: handle relative imports reaching outside working directory when using --incremental/--tsgo flags (#​2942)

  • fix: support SvelteKit zero types in svelte-check --incremental (#​2939)

v4.4.0

Compare Source

Minor Changes
  • feat: provide --incremental and --tsgo flags (#​2932)
Patch Changes
  • fix: ignore Unix domain sockets in file watcher to prevent crashes (#​2931)

  • fix: properly use machine output by default for Claude Code (e9f58d2)

v4.3.6

Compare Source

Patch Changes
  • fix: don't hoist type/snippet referencing $store (#​2926)

v4.3.5

Compare Source

Patch Changes
  • fix: ensure await-block type is preserved in the latest Svelte version (#​2895)

v4.3.4

Compare Source

Patch Changes
  • chore: use machine format when run by Claude Code (#​2870)

v4.3.3

Compare Source

Patch Changes
  • fix: prevent file watcher issue (#​2859)

  • fix: allow undefined and null values for #each in Svelte 5 (#​2863)

  • perf: check if file content changed in tsconfig file watch (#​2859)

v4.3.2

Compare Source

Patch Changes
  • perf: tweak some snapshot hot paths (#​2852)

  • perf: more precise module cache invalidation (#​2853)

  • fix: properly handle runes={false} in <svelte:options> (#​2847)

See https://github.com/sveltejs/language-tools/releases

v4.3.1

Compare Source

fix: handle object literal in MustacheTag (#​2805)

v4.3.0

Compare Source

  • feat: zero types for params (#​2795)
  • feat: add await support (#​2799)
  • fix: strip doctype using AST instead of regex (#​2798)
  • chore: make human output more concise and readable (#​2748)

v4.2.2

Compare Source

  • fix: invalidate project file cache and handle watcher race condition (#​2779)
  • fix: prevent error with bind:this={get, set} (#​2781)
  • fix: don't treat derived imported from svelte/store as a potential store (#​2780)
  • fix: key block can have its own block scope (#​2768)

v4.2.1

Compare Source

  • feat: support generics on snippets (#​2761)

v4.2.0

Compare Source

  • feat: support attachments (#​2760)
  • fix: deduplicate definition for rune-mode components (#​2759)

v4.1.7

Compare Source

  • fix: robustify hoisting logic around prop types (#​2740)
  • fix: ensure typed exports are marked as used (#​2746)
  • chore: bump vscode-html/css-language-service (#​2752)
  • fix: ensure eligible snippets can be referenced in module script (#​2753)
  • fix: prevent error with unclosed tag followed by LF or end of file (#​2750)

v4.1.6

Compare Source

  • fix: prevent unused variable error for bindable
  • fix: ensure exports in runes mode are marked as used
  • fix: add color CLI options

v4.1.5

Compare Source

  • fix: take other snippets into account when checking for hoistability (#​2668)
  • fix: disambiguate render in module script (#​2667)
  • fix: properly transform $props.id when $props is assigned to props (#​2694)
  • fix: handle booleanish popover (#​2702)
  • chore: bump vscode-html/css-language-service (#​2677)
  • fix: use referenced project's compiler option to get resolution mode (#​2676)

v4.1.4

Compare Source

  • fix: don't hoist types/snippets referencing stores or destructured variables (#​2661)

v4.1.3

Compare Source

  • fix: move snippets to correct place when only module script present

v4.1.2

Compare Source

  • feat: support generics attribute for JSDoc (#​2624)
  • fix: better snippet/interface hoistability analysis (#​2655)
  • chore: TypeScript 5.7 support (#​2585)

v4.1.1

Compare Source

  • fix: support each without as (#​2615)

v4.1.0

Compare Source

  • fix: don't move appended content from previous node while hoisting interface (#​2596)
  • fix: ensure hoisted interfaces are moved after hoisted imports (#​2597)
  • fix: preserve bind:... mapping on elements for better source maps
  • feat: prepare for some upcoming features of Svelte 5

v4.0.9

Compare Source

  • fix: detect shadowed variables/types during type hoisting (#​2590)

v4.0.8

Compare Source

  • fix: fall back to any instead of unknown for untyped $props (#​2582)
  • fix: robustify and fix file writing (#​2584)
  • fix: hoist types related to $props rune if possible (#​2571)

v4.0.7

Compare Source

  • fix: $props: infer types for $bindable, infer function type from arrow function

v4.0.6

Compare Source

  • chore: autotype const load = ... declarations (#​2540)
  • chore: provide component instance type in Svelte 5 (#​2553)
  • chore: support typescript 5.6 (#​2545)
  • fix: infer object and array shapes from fallback types (#​2562)

v4.0.5

Compare Source

  • fix: include named exports in svelte 5 type (#​2528)

v4.0.4

Compare Source

  • fix: relax component constructor type (#​2524)

v4.0.3

Compare Source

  • breaking(svelte5): only generate function component shape in runes mode (#​2517). This means you can no longer just do Component in type positions. Instead you need to prepend it with typeof. Here's how you do it:
    • ...when typing a component instance: Before: let x: Component. After: let x: ReturnType<typeof Component>
    • ...when typing a component constructor/function: Before let x: typeof Component. After let x: typeof Component (no change)
  • fix: revert additional two-way-binding checks as they were causing bugs (#​2508)
  • fix: include files indirectly belonging to a project into correct project (#​2488)
  • fix: check project files update more aggressively before assigning service (#​2518)
  • chore: upgrade to chokidar 4 (#​2502)

v4.0.2

Compare Source

  • fix: ensure components typed through Svelte 5's Component interface get proper intellisense

v4.0.1

Compare Source

  • fix: remove ancient process augmentation from internal d.ts file

v4.0.0

Compare Source

  • chore: bump magic-string (#​2476)
  • chore: switch from fast-glob to fdir (#​2433)
  • fix: detect <script module> tag (#​2482)
  • feat: better type checking for bindings in Svelte 5 (#​2477)
  • feat: replace svelte-preprocess with barebones TS preprocessor (#​2452)
  • feat: project reference support (#​2463)
Breaking changes
  • require Svelte 4 or later (#​2453)
  • make TypeScript a peer dependency, require TS 5 or later (#​2453)
  • require node 18 or later (#​2453)
  • process augmentation (declaring a process.browser field) was removed
  • slight changes to how files are assigned to which tsconfig.json (#​1234, #​2463)
  • slight changes to how Svelte module resolution works; .svelte files now take precedence over .svelte.js/ts files (if both exist) (#​2481)
  • language-server now forces fewer TypeScript options. Most notably skipLibCheck is no longer forced to true, which may result in d.ts files now being checked in your project, which they were not before, revealing type errors. Either fix those or add "skipLibCheck": true to your tsconfig.json (#​1976, #​2463)
sveltejs/svelte-preprocess (svelte-preprocess)

v6.0.5

Compare Source

Patch Changes
  • fix: correctly import transformer when automatically processing with TypeScript 6 (#​680)

v6.0.4

Compare Source

Patch Changes
  • fix: support TypeScript 6 (#​675)

v6.0.3

Compare Source

Bug Fixes

v6.0.2

Compare Source

Bug Fixes

v6.0.1

Compare Source

Bug Fixes

v6.0.0

Compare Source

BREAKING CHANGES
  • remove TS mixed imports support, require TS 5.0 or higher
  • remove preserve option as it's unnecessary
  • require Svelte 4+, Node 18+
  • add exports map
Bug Fixes
  • adjust globalifySelector to not split selectors with parentheses. (#​632) (c435ebd), closes #​501
  • fix: allow TS filename to be undefined, fixes #​488
  • fix: adjust Svelte compiler type import
  • fix: remove pug types and magic-string from dependencies
  • chore: bump peer deps, fixes #​553

5.1.4 (2024-04-16)

Bug Fixes

5.1.3 (2023-12-18)

Bug Fixes
  • sass dependency list referencing source file in win32 (#​621) (209312f)

5.1.2 (2023-12-12)

  • chore: mark postcss-load-config 5 as supported (3b5b1f0)

5.1.1 (2023-11-21)

Bug Fixes
  • force module(resolution) (66d3cf9)
tailwindlabs/tailwindcss (tailwindcss)

v4.3.3

Compare Source

Fixed
  • Support --watch --poll[=ms] in @tailwindcss/cli when filesystem events are unreliable or unavailable (#​20297)
  • Canonicalization: match arbitrary hex colors against theme colors case-insensitively (e.g. bg-[#fff] and bg-[#FFF]bg-white) (#​20298)
  • Prevent Preflight from overriding Firefox's native iframe:focus-visible outline styles (#​20292)
  • Ensure theme('colors.foo') in JS plugins resolves correctly when both --color-foo and --color-foo-bar exist (#​20299)
  • Ensure fractional opacity modifiers work with named shadow sizes like shadow-sm/12.5, text-shadow-sm/12.5, drop-shadow-sm/12.5, and inset-shadow-sm/12.5 (#​20302)
  • Parse selectors like [data-foo]div as two selectors instead of one (#​20303)
  • Ensure @tailwindcss/postcss rebuilds when a preprocessor like Sass changes the input CSS without changing the input file on disk (#​20310)
  • Ensure CSS nesting is handled even when Lightning CSS isn't run, such as in @tailwindcss/browser and Tailwind Play (#​20124)
  • Prevent achromatic theme colors from shifting hue when mixed in polar color spaces like oklch (#​20314)
  • Ensure --spacing(0) is optimized to 0px instead of 0 so it remains a <length> when used in calc(…) (#​20319)
  • Load @parcel/watcher only when needed in @tailwindcss/cli --watch mode, so one-off builds and --watch --poll work when @parcel/watcher can't be loaded (#​20325)
  • Use explicit platform fonts instead of system-ui and ui-sans-serif so CJK text respects the page's lang attribute on Windows (#​20318)
  • Prevent @tailwindcss/upgrade from rewriting ignored files when run from a subdirectory (#​20329)
  • Ensure earlier @source rules pointing to nested files are scanned when later @source rules point to files in parent folders (#​20335)
  • Prevent @tailwindcss/vite from triggering full page reloads when scanned files are processed by Vite but haven't been loaded as modules yet (#​20336)

v4.3.2

Compare Source

Fixed
  • Support bare spacing values for auto-rows-* and auto-cols-* utilities (e.g. auto-rows-12 and auto-cols-16) (#​20229)
  • Prevent @tailwindcss/cli in --watch mode from crashing on Windows when @source points to a directory that doesn't exist (#​20242)
  • Prevent @tailwindcss/vite from crashing in Deno v2.8.x when context.parentURL is not a valid URL (#​20245)
  • Ensure @tailwindcss/cli in --watch mode rebuilds when the input CSS file changes in an ignored directory (#​20246)
  • Allow @variant rules used in addBase(…) to use custom variants defined later (#​20247)
  • Prevent @tailwindcss/vite from crashing during HMR when scanned files or directories are deleted (#​20259)
  • Generate font-size instead of color declarations for text-[--spacing(…)] (#​20260)
  • Prevent @source patterns from scanning unrelated sibling files and folders (#​20263)
  • Extract class candidates adjacent to Template Toolkit delimiters like %]…[% in .tt, .tt2, and .tx files (#​20269)
  • Extract class candidates from conditional Maud syntax like p.text-black[condition] (#​20269)
  • Prevent @position-try rules from triggering unknown at-rule warnings when optimizing CSS (#​20277)
  • Support class suggestions for named opacity modifiers from --opacity theme values (#​20287)
  • Prevent type errors in @tailwindcss/postcss when used with newer PostCSS patch releases (#​20289)

v4.3.1

Compare Source

Added
  • Add --silent option to suppress output in @tailwindcss/cli (#​20100)
Fixed
  • Remove deprecation warnings by using Module#registerHooks instead of Module#register on Node 26+ (#​20028)
  • Canonicalization: don't crash when plugin utilities throw for unsupported values (#​20052)
  • Allow @apply to be used with CSS mixins (#​19427)
  • Ensure not-* correctly negates @container queries, including style(…) queries (#​20059)
  • Ensure drop-shadow-* color utilities work with custom shadow values containing calc(…) (#​20080)
  • Fix 'Sourcemap is likely to be incorrect' warnings when using @tailwindcss/vite (#​20103)
  • Ensure @tailwindcss/webpack can be installed in Rspack projects without requiring webpack as a peer dependency (#​20027)
  • Canonicalization: don't suggest invalid calc(…) expressions (e.g. px-[calc(1rem+0px)]px-[calc(1rem+0)]) (#​20127)
  • Canonicalization: avoid suggesting large spacing-scale values for arbitrary lengths (e.g. left-[99999px]left-[99999px], not left-24999.75) (#​20130)
  • Ensure @tailwindcss/cli in --watch mode recovers when a tracked dependency is deleted and restored (#​20137)
  • Ensure standalone @tailwindcss/cli binaries are ignored when scanning for class candidates (#​20139)
  • Ensure class candidates are extracted from Twig addClass(…) and removeClass(…) calls (#​20198)
  • Don't crash in the Ruby or Vue preprocessors when scanning files containing invalid UTF-8 bytes (#​19588)
  • Allow @variant to be used inside addBase (#​19480)
  • Ensure @source globs with symlinks are preserved (#​20203)
  • Ensure later @source rules can re-include files excluded by earlier @source not rules (#​20203)
  • Upgrade: don't migrate empty class rules to invalid @utility rules (#​20205)
  • Ensure transitions between inset-shadow-none and other inset shadows work correctly (#​20208)
  • Ensure explicitly referenced @source directories are scanned even when ignored by git (#​20214)
  • Ensure @source globs ending in **/* preserve dynamic path segments to avoid scanning too many files (#​20217)
  • Canonicalization: don't fold calc(…) divisions when the result would require high precision (e.g. w-[calc(100%/3.5)]w-[calc(100%/3.5)], not w-[28.571428571428573%]) (#​20221)
  • Serve ESM type declarations to ESM importers of @tailwindcss/postcss (#​20228)
Changed
  • Generate 0 instead of calc(var(--spacing) * 0) for spacing utilities like m-0 and left-0 (#​20196)
  • Generate var(--spacing) instead of calc(var(--spacing) * 1) for spacing utilities like m-1 and left-1 (#​20196)

v4.3.0

Compare Source

Added
  • Add @container-size utility (#​18901)
  • Add scrollbar-{auto,thin,none} utilities for scrollbar-width, and scrollbar-thumb-* / scrollbar-track-* color utilities for scrollbar-color (#​19981, #​20019)
  • Add scrollbar-gutter-* utilities (#​20018)
  • Add zoom-* utilities (#​20020)
  • Add tab-* utilities (#​20022)
  • Allow using @variant with stacked variants (e.g. @variant hover:focus { … }) (#​19996)
  • Allow using @variant with compound variants (e.g. @variant hover, focus { … }) (#​19996)
  • Support --default(…) in --value(…) and --modifier(…) for functional @utility definitions (#​19989)
Fixed
  • Ensure @plugin resolves package JavaScript entries instead of browser CSS entries when using @tailwindcss/vite (#​19949)
  • Fix relative @import and @plugin paths resolving from the wrong directory when using @tailwindcss/vite (#​19965)
  • Ensure CSS files containing @variant are processed by @tailwindcss/vite (#​19966)
  • Resolve imports relative to base when result.opts.from is not provided when using @tailwindcss/postcss (#​19980)
  • Canonicalization: preserve significant _ whitespace in arbitrary values (#​19986)
  • Canonicalization: add parentheses when removing whitespace from arbitrary values would hurt readability (e.g. w-[calc(100%---spacing(60))]w-[calc(100%-(--spacing(60)))]) (#​19986)
  • Canonicalization: preserve the original unit in arbitrary values instead of normalizing to base units (e.g. -mt-[20in]mt-[-20in], not mt-[-1920px]) (#​19988)
  • Canonicalization: migrate arbitrary :has() variants from [&:has(…)] to has-[…] (#​19991)
  • Upgrade: don’t migrate inline style attributes (e.g. style="flex-grow: 1"style="flex-grow: 1", not style="grow: 1") (#​19918)
  • Allow multiple @utility definitions with the same name but different value types ([#​19777](https:/

Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot requested a review from a team as a code owner October 6, 2025 07:39
@coderabbitai

coderabbitai Bot commented Oct 6, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

This PR upgrades dependencies in the UI package. The OpenAI dependency is bumped from 5.23.2 to 6.5.0 in both the import map and package.json. Additional devDependencies are also updated: svelte-check, svelte-preprocess, and tailwindcss to newer minor and patch versions.

Changes

Cohort / File(s) Summary
UI package dependency updates
packages/ui/import_map.json, packages/ui/package.json
Upgraded openai from 5.23.2 to 6.5.0; upgraded svelte-check from ^3.8.6 to ^4.3.3; upgraded svelte-preprocess from ^5.1.4 to ^6.0.3; upgraded tailwindcss from ^3.4.18 to ^4.1.14

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested reviewers

  • ericglau
  • collins-w
🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
Title check ✅ Passed The title clearly identifies a major update to UI dependencies, which matches the main changeset.
Description check ✅ Passed The description directly documents the UI dependency updates and includes relevant release notes and configuration details.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch renovate/major-ui-deps-sync

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@renovate
renovate Bot force-pushed the renovate/major-ui-deps-sync branch 5 times, most recently from e49ac46 to 394311c Compare October 8, 2025 16:38
@socket-security

socket-security Bot commented Oct 8, 2025

Copy link
Copy Markdown

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Block Low
Potential code anomaly (AI signal): npm cbor2 is 65.0% likely to have a medium risk anomaly

Notes: Overall, the codebase appears to be a robust, feature-rich CBOR serialization library with extensive tag support and defensive input handling. There is no concrete evidence of malicious behavior or data exfiltration within the provided fragment. The main operational risk is inherent to any data-serialization component: untrusted inputs can trigger potentially expensive or error-prone constructions (URL/RegExp/Date) if downstream usage is insecure. The code mitigates this with strict validations and explicit error handling.

Confidence: 0.65

Severity: 0.52

From: yarn.locknpm/ava@8.0.1npm/cbor2@2.3.0

ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/cbor2@2.3.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Low
Potential code anomaly (AI signal): npm glob is 68.0% likely to have a medium risk anomaly

Notes: The Glob utilities implement a conventional and well-structured filesystem glob-walking mechanism with robust control flow (abort signals, backpressure) and safe output semantics. There is no evidence of malicious behavior, backdoors, or data exfiltration within this fragment. Risks mainly relate to how downstream consumers may handle emitted paths, not to the library itself.

Confidence: 0.68

Severity: 0.50

From: yarn.locknpm/ava@8.0.1npm/glob@13.0.6

ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/glob@13.0.6. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@renovate
renovate Bot force-pushed the renovate/major-ui-deps-sync branch 7 times, most recently from ab19736 to e5f0fb6 Compare October 15, 2025 13:35
@renovate
renovate Bot force-pushed the renovate/major-ui-deps-sync branch 3 times, most recently from 2f3fb12 to 9c27729 Compare October 17, 2025 20:04

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
packages/ui/package.json (1)

15-45: Critical: Tailwind v4 migration incomplete—build will fail due to missing configuration updates.

The upgrade to Tailwind v4 requires configuration and CSS syntax changes that are not present in this PR:

  1. Missing required dependency: @tailwindcss/postcss not in package.json. Tailwind v4 moved the PostCSS plugin to a separate package; your postcss.config.js requires 'tailwindcss' which no longer exists as a plugin.

  2. Outdated CSS directives:

    • packages/ui/src/common/styles/global.css: Change @tailwind utilities; to @import "tailwindcss";
    • packages/ui/src/common/styles/standalone.css: Likely needs same update
  3. Incompatible preprocessor config: packages/ui/svelte.config.js has postcss: true which will fail when PostCSS can't load the tailwindcss plugin.

Required changes before merge:

  • Add "@tailwindcss/postcss": "next" to devDependencies (or use CSS-first approach by removing postcss config entirely)
  • Update all CSS files from @tailwind directives to @import "tailwindcss"
  • Run npm run build and npm run validate to verify the build succeeds
  • Confirm svelte-check passes with Svelte v3.55.0 + svelte-check v4.3.3

The OpenAI SDK upgrade (v5.23.2→6.5.0) appears compatible with your usage patterns.

🧹 Nitpick comments (1)
packages/ui/package.json (1)

29-29: Consider using a caret range for OpenAI to allow patch/minor updates.

The version is pinned to an exact semver (6.5.0) rather than using a caret range (^6.5.0). While pinning prevents accidental upgrades, it also blocks security patches and minor updates. Most projects use caret ranges for npm dependencies to balance safety and flexibility. If exact pinning is intentional, please document the rationale.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8073313 and 9c27729.

⛔ Files ignored due to path filters (1)
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
📒 Files selected for processing (2)
  • packages/ui/import_map.json (1 hunks)
  • packages/ui/package.json (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (10)
  • GitHub Check: boostsecurity - boostsecurityio/semgrep-pro
  • GitHub Check: check
  • GitHub Check: build (cairo, default)
  • GitHub Check: build (solidity, default)
  • GitHub Check: build (stellar, default)
  • GitHub Check: build (stellar, compile)
  • GitHub Check: build (stylus, default)
  • GitHub Check: format-lint
  • GitHub Check: mcp
  • GitHub Check: semgrep-cloud-platform/scan
🔇 Additional comments (2)
packages/ui/import_map.json (1)

4-4: Verify OpenAI SDK v6 compatibility—significant API migration required.

The OpenAI SDK v6 migrated from node-fetch to builtin fetch, which represents a breaking change. Before merging, you must verify that:

  1. All application code consuming the OpenAI SDK has been updated to work with v6's API (e.g., method signatures, response shapes)
  2. The application builds successfully with the new version
  3. Existing tests pass with v6

Since the PR context shows no code changes related to OpenAI usage, there's a risk that dependent code is incompatible with v6.

packages/ui/package.json (1)

39-40: Verify Svelte ecosystem upgrade—ensure build tools meet minimum requirements.

Svelte 4 is mainly a maintenance release that increases the minimum version requirements, with Node.js 16 now the minimum version and TypeScript 5+ recommended. The package.json shows TypeScript ^5.9.3 (line 44), which satisfies requirements.

However, verify that:

  1. The application builds successfully with svelte-check ^4.3.3
  2. If using SvelteKit, it's version 1.20.4 or newer (check if applicable)
  3. The validate script at line 12 (svelte-check) runs without errors

Comment thread packages/ui/package.json Outdated
"tailwindcss": "^3.4.18",
"svelte-check": "^4.3.3",
"svelte-preprocess": "^6.0.3",
"tailwindcss": "^4.1.14",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

⚠️ Tailwind CSS v4 requires significant configuration and CSS file updates—verify migration is complete.

Tailwind CSS v4.0 is a major version with necessary updates required from v3 to v4. This update introduces breaking changes that are NOT evident in this PR:

  1. CSS imports: In v4 you import Tailwind using a regular CSS @import statement, not using the @tailwind directives
  2. Preprocessor incompatibility: Tailwind CSS v4.0 is not designed to be used with CSS preprocessors like Sass, Less, or Stylus, and it is not possible to use Sass for <style> blocks in Svelte
  3. Browser support: Tailwind CSS v4.0 is designed for Safari 16.4+, Chrome 111+, and Firefox 128+. If you need to support older browsers, stick with v3.4
  4. Configuration: CSS-first config replaces JavaScript-based tailwind.config.js

The PR shows no corresponding updates to CSS files, Tailwind config, or SCSS/Sass removal. The upgrade tool will handle most of these changes automatically, but there's no evidence it was used. Without these changes, the build will likely fail or styles will break.

Verify the following before merging:

  • All CSS files have been updated to use @import "tailwindcss" instead of @tailwind directives
  • tailwind.config.js has been updated to CSS-first format (or removed if no custom config needed)
  • Any SCSS/Sass files have been converted to plain CSS or removed
  • The build completes successfully and styles render correctly

Run the following verification script:


🏁 Script executed:

#!/bin/bash
# Find and list Tailwind-related config and CSS files

echo "=== Tailwind Config Files ==="
find . -name "tailwind.config.*" -o -name "tailwind.css" -o -name "global.css" | grep -v node_modules

echo ""
echo "=== SCSS/Sass Files (may be incompatible with Tailwind v4) ==="
find . -name "*.scss" -o -name "*.sass" | grep -v node_modules | head -20

echo ""
echo "=== CSS Files Mentioning @tailwind ==="
rg -t css "@tailwind" --no-heading

echo ""
echo "=== SVG/Vue/Svelte Files with Style Blocks Using @tailwind ==="
rg -t svelte -A2 "<style" | grep -A2 "@tailwind"

Length of output: 418


CSS files must be updated to use Tailwind v4 syntax—@tailwind directives are no longer supported.

In v4 you import Tailwind using a regular CSS @import statement, not using the @tailwind directives you used in v3. The PR updates tailwindcss to v4.1.14 but contains two CSS files that still use the deprecated v3 syntax:

  • packages/ui/src/standalone.css:@tailwind utilities;
  • packages/ui/src/common/styles/global.css:@tailwind utilities;

These files must be updated before this PR can be merged. Change @tailwind utilities; to @import "tailwindcss"; in both files.

Additional items to verify:

  • If tailwind.config.js contains custom configuration, it must be explicitly loaded with @config "../../tailwind.config.js"; at the top of your CSS file (or migrated to CSS-first format using @theme)
  • Ensure tailwind.config.js is no longer auto-detected in v4 and add the @config directive if needed
  • If any .svelte, .vue, or other component files use <style> blocks with Tailwind, verify they reference the updated CSS or use the new v4 syntax

@renovate
renovate Bot force-pushed the renovate/major-ui-deps-sync branch 6 times, most recently from e3ed09e to 65753f3 Compare October 24, 2025 14:45
@renovate
renovate Bot force-pushed the renovate/major-ui-deps-sync branch 5 times, most recently from 574305a to 84def4e Compare October 30, 2025 12:52
@renovate
renovate Bot force-pushed the renovate/major-ui-deps-sync branch 5 times, most recently from 856b623 to 9ab9475 Compare November 18, 2025 03:44
@renovate
renovate Bot force-pushed the renovate/major-ui-deps-sync branch 7 times, most recently from 9ceae70 to e56267c Compare December 1, 2025 18:54
@renovate
renovate Bot force-pushed the renovate/major-ui-deps-sync branch 4 times, most recently from 886ad57 to 98f9d30 Compare December 9, 2025 16:52
@renovate
renovate Bot force-pushed the renovate/major-ui-deps-sync branch 5 times, most recently from b394213 to 6bad696 Compare December 16, 2025 20:55
@renovate
renovate Bot force-pushed the renovate/major-ui-deps-sync branch 2 times, most recently from ed2eab4 to d865f3b Compare December 20, 2025 08:50
@renovate
renovate Bot force-pushed the renovate/major-ui-deps-sync branch 5 times, most recently from bed7122 to 67c2053 Compare January 12, 2026 17:31
@socket-security

socket-security Bot commented Jun 4, 2026

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants